@kasperpeulen @ndelangen given that we now provide a way to get templates from a community package, I wonder if the ts directory name change impacted them? Maybe we should also try and fallback to cli/template/ts?

Tagging @IanVS as he was involved in changing the template names

Ah, yeah my PR started out to only handle ts-legacy templates, and it evolved from there so I guess I missed all the normal ts folders in renderers that didn't have ts-legacy.

we now provide a way to get templates from a community package

Can you point me to how that's documented? Do we know of any packages doing this so far?

I think we should be clear for anyone creating a community template that can be installed via the CLI what the correct template directory names should be, but I think it's also good to allow a fallback if they don't completely follow it. @jonniebigodes do we have documentation for the community building new frameworks to install via our CL? I'm not sure where I'd even look for that.

I agree. We do have a fallback mechanism, but honestly I think there's no documentation anywhere 😓

@yannbf and @IanVS, we have the get started guide on building a framework here, but we don't have anything related to this. We'll need to expand that one and provide a more technical approach to how to build a framework and feature also the CLI templates as a part of it, mostly because it's where users will find out how to write stories for their components using a framework.